Reorganize doc index, add pointer guide #11364
Conversation
| } | ||
| ~~~ | ||
|
|
||
| But won't this be inefficent? Well, that's a complicated question, but it's |
There was a problem hiding this comment.
Inefficiency isn't the only reason to pass by reference: ownership is the main one, and I feel this section is totally ignoring that.
There was a problem hiding this comment.
Agreed; most tutorial (e.g. for C) introduce pointers as a way to pass a variable to a function to edit it directly (well also as a way to workaround the inability to return multiple values in the case of C, which does not have tuples).
Maybe this can be adressed later on.
|
Thanks for the spellcheck everyone! At the time I wrote this, I thought it was enabled, but wasn't. :/ Yay typos! All these changes seem good. |
|
I will make all the recommended changes in a followup. |
This reorganizes the documentation index to be more focused on the in-tree docs, and to clean up the style, and it also adds @steveklabnik's pointer guide.
|
It looks like these comments are addressed in #11388? |
|
Not all. But I think #11397 addresses the rest. |
|
Can confirm, #11397 addresses all of the typos and markdown errors that I could find. |
This reorganizes the documentation index to be more focused on the in-tree docs, and to clean up the style, and it also adds @steveklabnik's pointer guide.